Update CC versionto 0.7.0

ANTIALIAS was removed in Pillow 10.0.0 (after being deprecated through many previous versions). Now you need to use PIL.Image.LANCZOS or PIL.Image.Resampling.LANCZOS.

(This is the exact same algorithm that ANTIALIAS referred to, you just can no longer access it through the name ANTIALIAS.)

Manifest keys should be sorted: domain, name, then alphabetical order

…n mismatch

This will allow the user to set up an external reverse proxy to have the HA instance operate on HTTPS and push_image use that reverse proxy to avoid using HTTPS traffic processing on the plate.

PIL uses a width,height tuple for resize() and thumbnail().

…e-bind-hass-and-hass-components

Reuse of the same image with different sized displays causes a random resize.

Dynamic reloading broken on recently added displays.

Update manifest version

Added optional setting http_proxy to push_image

…red and started. This should also fix #133 but needs testing by someone who had the MQTT error (I did not, I actually never have).

Fix: Unexpected string in integer variable due to mqtt not being ready at startup.

…_forward_entry_setups`

This commit addresses two deprecation warnings in the openHASP integration:

1. **Entity Service Schema**  
   Home Assistant 2025.9 and onward no longer allows registering entity services
   with an empty `{}` schema. This commit adds minimal entity service schemas
   for `SERVICE_WAKEUP`, `SERVICE_PAGE_NEXT`, and `SERVICE_PAGE_PREV` by using
   `cv.make_entity_service_schema({})`. Additionally, the existing `PUSH_IMAGE`
   service is updated to use `cv.make_entity_service_schema(...)` to ensure
   compliance with future HA releases.

2. **async_forward_entry_setup Deprecation**  
   Replaces multiple `await hass.config_entries.async_forward_entry_setup(entry, domain)`
   calls in a loop with a single `await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)`.
   This ensures the setup lock is handled correctly and removes the related
   deprecation warning.

These changes make the custom component compatible with the upcoming breaking
changes in Home Assistant 2025.x and beyond, preventing warnings and ensuring a
smooth user experience.

Limit version parsing to major, minor and patch digits, other items are discarded.

Bump version number

In Home Assistant 2024.x and later, the OptionsFlow base class provides
config_entry as a read-only property. The previous implementation tried
to set self.config_entry in __init__, which fails with:

    AttributeError: property 'config_entry' of 'OpenHASPOptionsFlowHandler'
    object has no setter

This caused a 500 Internal Server Error when clicking the gear icon to
configure any openHASP device in the integration settings.

Fix: Remove the custom __init__ method and don't pass config_entry to the
constructor. The base class automatically provides self.config_entry.

…rvices

Per dgomes' feedback, updated ALL entity services to use
cv.make_entity_service_schema() for consistency, not just the ones
with empty schemas.

This fixes:
- Variable naming bug (WAKEUP_SERVICE_SCHEMA vs WAKEUP_SCHEMA)
- Applies consistent schema wrapping to PAGE_CHANGE, LOAD_PAGE,
  CLEAR_PAGE, COMMAND, and CONFIG services

Use proper entity service schemas & replace async_forward_entry_setup with async_forward_entry_setups

…-setter

Fix OptionsFlow config_entry setter error in Home Assistant 2024.x+

Support to handle custom commands.
https://github.com/HASwitchPlate/openHASP/blob/26671370f527d70b5b1a737833a8a78085c543b2/src/hasp/hasp_dispatch.cpp#L455

Fix for [HA Core 2025.3 Warning: HASPLight does not report a color mode #161